Searched hist:"636192 c4" (Results 1 – 3 of 3) sorted by relevance
/qemu/tests/qemu-iotests/ |
H A D | 223 | 636192c4 Fri Jan 11 19:47:20 GMT 2019 Eric Blake <eblake@redhat.com> qemu-nbd: Add --bitmap=NAME option
Having to fire up qemu, then use QMP commands for nbd-server-start and nbd-server-add, just to expose a persistent dirty bitmap, is rather tedious. Make it possible to expose a dirty bitmap using just qemu-nbd (of course, for now this only works when qemu-nbd is visiting a BDS formatted as qcow2).
Of course, any good feature also needs unit testing, so expand iotest 223 to cover it.
Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20190111194720.15671-9-eblake@redhat.com>
|
H A D | 223.out | 636192c4 Fri Jan 11 19:47:20 GMT 2019 Eric Blake <eblake@redhat.com> qemu-nbd: Add --bitmap=NAME option
Having to fire up qemu, then use QMP commands for nbd-server-start and nbd-server-add, just to expose a persistent dirty bitmap, is rather tedious. Make it possible to expose a dirty bitmap using just qemu-nbd (of course, for now this only works when qemu-nbd is visiting a BDS formatted as qcow2).
Of course, any good feature also needs unit testing, so expand iotest 223 to cover it.
Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20190111194720.15671-9-eblake@redhat.com>
|
/qemu/ |
H A D | qemu-nbd.c | 636192c4 Fri Jan 11 19:47:20 GMT 2019 Eric Blake <eblake@redhat.com> qemu-nbd: Add --bitmap=NAME option
Having to fire up qemu, then use QMP commands for nbd-server-start and nbd-server-add, just to expose a persistent dirty bitmap, is rather tedious. Make it possible to expose a dirty bitmap using just qemu-nbd (of course, for now this only works when qemu-nbd is visiting a BDS formatted as qcow2).
Of course, any good feature also needs unit testing, so expand iotest 223 to cover it.
Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20190111194720.15671-9-eblake@redhat.com>
|